🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

Documentation changes preview: https://docs-v3-preview.elastic.dev/elastic/ecs/pull/2638/reference/

ECS PR Triage (automated)

PR Triage Report

PR: #2638 — [main] (forwardport #2636) Release notes for 9.4
Classification: Direct PR
Change type: Documentation
Scope: Minor

Summary

This is an automated Mergify forward-port of PR #2636, adding release notes for ECS 9.4.0 to docs/release-notes/index.md. The change is purely additive documentation — a new release-notes section summarizing features already merged. It touches no schema files, no tooling, and no generated artifacts. This is a standard release-process PR and is always routed as a Direct PR per classification-rules §0 and §2.

Files changed

• Schemas: none
• Generated: none
• Tooling/scripts/tests: none
• Docs (hand-authored): docs/release-notes/index.md (+9 lines — new 9.4.0 release notes section)
• CI / GitHub: none
• RFCs: none

Routing decision

Direct PR — This PR exclusively touches release mechanics (adding release notes for version 9.4.0). Per classification-rules §0, release process PRs are always Direct PR regardless of content. Additionally, per §2, hand-authored documentation changes that are not generated reference files are low-risk and non-controversial. No RFC or discussion is needed.

Risk notes

• Breaking / deprecation: No. The change is additive release-note text only.
• OTel / semconv: N/A — no schema or field changes.
• Scope / reuse: N/A — no fieldset, reuse, or categorization changes.

Completeness checklist

• PR description (all sections) — The PR is an automated Mergify forward-port; the minimal body referencing the source PR Release notes for 9.4 #2636 is acceptable for bot-generated release-process PRs. The standard 7-section template is not expected for automated forward-ports.
• CHANGELOG.next.md — Not required. This PR does not touch schemas/ or scripts/; it is a pure documentation/release-notes change.
• make + committed generated outputs — Not required. No schema changes were made.
• OTel otel: on new/changed semconv-related fields — N/A. No fields added or changed.
• Tests / make check — Not required for a documentation-only release-notes addition.
• CLA (contributor) — Automated by Mergify bot; CLA not applicable for bot-authored forward-ports.

Recommended next actions

1. Reviewer: Verify the 9.4.0 release note entries accurately reflect the features shipped (PRs Add field maturity and remove experimental pipeline #2599, Increase total fields limit from 2000 to 2500 #2584). Cross-check against the actual merged changes.
2. Reviewer: Confirm the anchor IDs (ecs-9-4-0-release-notes, ecs-9-4-0-features-enhancements) follow the existing naming convention in docs/release-notes/index.md.
3. Merge: This is a straightforward, low-risk forward-port. Approve and merge when content accuracy is confirmed.

Posted by PR Triage workflow

🔍 Preview links for changed docs

• docs/release-notes/index.md

✅ Vale Linting Results

No issues found on modified lines!

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.